fix: only show dropdown when focusing input #100
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #99
Currently, Typeahead results would display even when the input field doesn't have focus (reacting to
valuechanges). This was particularly problematic in scenarios with dependent Typeahead components where values are set programmatically. When a parent Typeahead selection automatically populated a child Typeahead with a single matching result, that result would incorrectly display even though the user hadn't interacted with the child input.From a UX standpoint, it makes sense to only show results when the current input is focused. This, however, renders the current
showDropdownOnFocusa no-op. It may need to be inverted (e.g., show menu if input has value).// Before: results could show without focus $: showResults = !hideDropdown && results.length > 0; $: if (showDropdownOnFocus) { showResults = showResults && isFocused; } // After: results always require focus $: showResults = !hideDropdown && results.length > 0 && isFocused;This ensures results only appear when users are actively interacting with the input, preventing unwanted dropdown displays in programmatic usage scenarios.